Program tracing for time travel debugging and analysis

ABSTRACT

Recording a replay-able trace of execution of a multi-threaded process includes identifying a trace memory model that defines one or more orderable events that are to be ordered across a plurality of threads of the multi-threaded process. The plurality of threads are executed concurrently across one or more processing units of one or more processors. During execution of the plurality of threads, a separate replay-able trace is recorded for each thread independently. Recording includes, for each thread, recording initial state for the thread, recording at least one memory read performed by at least one processor instruction executed by the thread that takes memory as input, and recording a least one orderable event performed by the thread with a monotonically increasing number that orders the event among other orderable events across the plurality of threads.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No. 15/252,998, filed Aug. 31, 2016, entitled “PROGRAM TRACING FOR TIME TRAVEL DEBUGGING AND ANALYSIS,” and which issues as U.S. Pat. No. 10,042,737 on Aug. 7, 2018. The entire contents of the forgoing application are incorporated by reference herein in their entirety.

BACKGROUND

When writing source code during the development of software applications, developers commonly spend a significant amount of time “debugging” the source code to find runtime errors in the code. For example, a developer may take several approaches to reproduce and localize a source code bug, such as observing behavior of a program based on different inputs, inserting debugging code (e.g., to print variable values, to track branches of execution, etc.), temporarily removing code portions, etc. Tracking down runtime errors to pinpoint code bugs can occupy a significant portion of application development time.

Debugging applications (“debuggers”) have been developed in order to assist with the code debugging process. Many such tools offer the ability to trace, visualize, and alter the execution of computer code. For example, debuggers may visualize the execution of code instructions (e.g., source code, assembly code, etc.) and variable values, and enable the user to alter aspects of the code execution. Commonly, debuggers enable a user to set “breakpoints” in source code (e.g., a particular instruction or statement in source code) which, when reached during execution, cause execution of the program to be suspended. When source code execution is suspended, a user may be presented variable values and be given options to choose how to proceed (e.g., by terminating execution, by continuing execution as normal, by stepping into, over, or out of statements/function calls, etc.). However, classic debuggers only enable code execution to be observed/altered in a single direction—forward. For example, classic debuggers do not enable a user to choose to go back to a prior breakpoint.

An emerging form of debugging is “time travel” debugging, in which execution of a program is recorded into a trace, which can be then be replayed and analyzed both forwards and backwards.

BRIEF SUMMARY

Embodiments herein are directed to new implementations of recording and replaying traces for time travel debugging that can produce orders-of-magnitude performance improvements over prior attempts, that enable recording of multi-threaded programs whose threads freely run concurrently across multiple processing units, and that can produce trace files with orders of magnitude size reduction over the trace files of prior attempts.

In some embodiments, a method for recording a replay-able trace of execution of a multi-threaded process includes identifying a trace memory model that defines one or more orderable events that are to be ordered across a plurality of threads of the multi-threaded process. The method also includes executing the plurality of threads concurrently across one or more processing units of the one or more processors, and, during execution of the plurality of threads, recording a separate replay-able trace for each thread independently. Recording a separate replay-able trace for each thread includes recording initial state for the thread. Recording a separate replay-able trace for each thread also includes recording at least one memory read performed by at least one processor instruction executed by the thread that takes memory as input. Recording a separate replay-able trace for each thread also includes recording a least one orderable event performed by the thread with a monotonically increasing number that orders the event among other orderable events across the plurality of threads.

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which the above-recited and other advantages and features of the invention can be obtained, a more particular description of the invention briefly described above will be rendered by reference to specific embodiments thereof which are illustrated in the appended drawings. Understanding that these drawings depict only typical embodiments of the invention and are not therefore to be considered to be limiting of its scope, the invention will be described and explained with additional specificity and detail through the use of the accompanying drawings in which:

FIG. 1 illustrates an example computer architecture in which embodiments of time travel debugging may operate;

FIG. 2 illustrates a flow chart of an example method for recording a replay-able trace of execution of a multi-threaded process;

FIG. 3 example of ordering events across concurrently executing threads;

FIG. 4 illustrates an example of use of a shadow copy;

FIG. 5 illustrates an example of a ring buffer;

FIG. 6 illustrates an example computer architecture for processor cache based tracing; and

FIG. 7 illustrates a flow chart of an example method for recording a replay-able trace of execution of an executable entity using cache data.

DETAILED DESCRIPTION

Embodiments herein are directed to new implementations of recording and replaying traces for time travel debugging that can produce orders-of-magnitude performance improvements over prior attempts, that enable recording of multi-threaded programs whose threads freely run concurrently across multiple processing units, and that can produce trace files with orders of magnitude size reduction over the trace files of prior attempts.

Generally, a goal of time travel debugging is to capture in a trace which processor instructions an executable entity (e.g., user-mode threads, kernel threads, a hypervisor, etc.) executes, such that these instructions can be replayed from the trace with absolute precision at a later time, at whatever granularity is needed. Being able to replay every instruction executed as part of application code enables the illusion of backwards replay of the application later. For example, to hit a breakpoint in the backwards direction, the trace is replayed from a time prior to the breakpoint, and the replay stops at the last time that breakpoint hits that is before where the debugger is currently analyzing the code stream.

Prior attempts to provide time travel debugging have suffered from several compromises that have led to limited adoption. For example, prior attempts apply significant restrictions on code execution, such as requiring a trace to include a strict ordering of all the instructions executed (i.e., a fully sequentially consistent recording model). This is accomplished, for example, by requiring that multi-threaded programs be executed non-concurrently on a single core, or by requiring that program instructions be executed non-concurrently in lock-step on multiple cores (e.g., execute N instructions on one processor core, then N on another processor core, and so on). These are significant limitations in view of today's highly multi-threaded code and highly parallel multi-core and hyper-threaded processors. Further, prior attempts cause significant program performance degradation, and typically produce exceptionally large trace files (particularly when emulating multiple cores), at least in part because they deterministically record the execution of each and every instruction, and create a comprehensive record of full memory state during program execution. Each of the foregoing has made prior attempts at time travel debugging both exceptionally slow, and unrealistic for both use in production environments and for long-term tracing of program execution, especially for applications having many threads running concurrently.

Operating Environment

Initially, FIG. 1 illustrates an example computing environment 100 in which embodiments of time travel debugging may operate according to the present invention. Embodiments of the present invention may comprise or utilize a special-purpose or general-purpose computer system 101 that includes computer hardware, such as, for example, one or more processors 102, system memory 103, one or more data stores 104, and/or input/output hardware 105.

Embodiments within the scope of the present invention include physical and other computer-readable media for carrying or storing computer-executable instructions and/or data structures. Such computer-readable media can be any available media that can be accessed by the computer system 101. Computer-readable media that store computer-executable instructions and/or data structures are computer storage devices. Computer-readable media that carry computer-executable instructions and/or data structures are transmission media. Thus, by way of example, and not limitation, embodiments of the invention can comprise at least two distinctly different kinds of computer-readable media: computer storage devices and transmission media.

Computer storage devices are physical hardware devices that store computer-executable instructions and/or data structures. Computer storage devices include various computer hardware, such as RAM, ROM, EEPROM, solid state drives (“SSDs”), flash memory, phase-change memory (“PCM”), optical disk storage, magnetic disk storage or other magnetic storage devices, or any other hardware device(s) which can be used to store program code in the form of computer-executable instructions or data structures, and which can be accessed and executed by the computer system 101 to implement the disclosed functionality of the invention. Thus, for example, computer storage devices may include the depicted system memory 103 and/or the depicted data store 104 which can store computer-executable instructions and/or data structures.

Transmission media can include a network and/or data links which can be used to carry program code in the form of computer-executable instructions or data structures, and which can be accessed by the computer system 101. A “network” is defined as one or more data links that enable the transport of electronic data between computer systems and/or modules and/or other electronic devices. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a computer system, the computer system may view the connection as transmission media. Combinations of the above should also be included within the scope of computer-readable media. For example, the input/output hardware 105 may comprise hardware (e.g., a network interface module (e.g., a “NIC”)) that connects a network and/or data link which can be used to carry program code in the form of computer-executable instructions or data structures.

Further, upon reaching various computer system components, program code in the form of computer-executable instructions or data structures can be transferred automatically from transmission media to computer storage devices (or vice versa). For example, computer-executable instructions or data structures received over a network or data link can be buffered in RAM within a NIC (e.g., input/output hardware 105), and then eventually transferred to the system memory 103 and/or to less volatile computer storage devices (e.g., data store 104) at the computer system 101. Thus, it should be understood that computer storage devices can be included in computer system components that also (or even primarily) utilize transmission media.

Computer-executable instructions comprise, for example, instructions and data which, when executed at the one or more processors 102, cause the computer system 101 to perform a certain function or group of functions. Computer-executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, or even source code.

Those skilled in the art will appreciate that the invention may be practiced in network computing environments with many types of computer system configurations, including, personal computers, desktop computers, laptop computers, message processors, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile telephones, PDAs, tablets, pagers, routers, switches, and the like. The invention may also be practiced in distributed system environments where local and remote computer systems, which are linked (either by hardwired data links, wireless data links, or by a combination of hardwired and wireless data links) through a network, both perform tasks. As such, in a distributed system environment, a computer system may include a plurality of constituent computer systems. In a distributed system environment, program modules may be located in both local and remote memory storage devices.

As illustrated, the data store 104 can store computer-executable instructions and/or data structures representing a time travel debugger 106 and application code 107 that is the subject of tracing/debugging by the time travel debugger 106. When these programs are executing (e.g., using the processor(s) 102), the system memory 103 can store corresponding runtime data, such as runtime data structures, computer-executable instructions, etc. Thus, FIG. 1 illustrates the system memory 103 as including time travel debugger runtime data 106′ and application code runtime data 107′.

As depicted, the time travel debugger 106 includes one or more components or modules, such as a record component 106 a and a replay component 106 b. At appropriate times, these components may also include corresponding runtime data (illustrated as record runtime data 106 a′ and replay runtime data 106 b′) in the system memory 103. During execution, the record component 106 a/record runtime data 106 a′ records one or more trace file(s) 108 documenting execution of the application code 107 at the processor(s) 102. Later, the replay module 106 b/replay runtime data 106 b′ can use the trace file(s) 108, in connection with the application code 107, to replay execution of the application code 107 both forwards and backwards. While the trace file(s) 108 are depicted as being stored in the data store 104, these trace file(s) 108 may also be recorded, at least temporarily, in the system memory 103 or at some other storage device. It is noted that the record component 106 a may exist at one computer system, and the replay component 106 b may exist at another computer system. As such, execution of a program may be traced/recorded on one system, and replayed on another system.

FIG. 1 includes a general representation of the internal hardware components of the processors(s) 102. As illustrated, the processors(s) 102 include one or more processing units 102 a (i.e., cores). Each processing unit 102 a comprises hardware logic that executes processor instructions that are defined by applications, and which instructions are selected from among a predefined processor instruction set architecture. The particular instruction set architecture of the processors(s) 102 varies based on processor manufacturer and processor model. Common instruction set architectures include the IA-64 and IA-32 architectures from INTEL, INC., the AMD64 architecture from ADVANCED MICRO DEVICES, INC., and various Advanced RISC Machine (“ARM”) architectures from ARM HOLDINGS, PLC, although a great number of other instruction set architectures exist and can be used by the present invention. In general, an “instruction” is the smallest externally-visible (i.e., external to the processor) unit of code that is executable by a processor.

The processing units 102 a obtain the processor instructions from a cache 102 b and execute the processor instructions based on data in the cache 102 b based on data in registers 102 c, and/or without input data. In general, the cache 102 b is a small amount (i.e., small relative to the typical amount of system memory 103) of random-access memory that stores on-processor copies of portions of the system memory 103. For example, when executing the application code 107, the cache 102 b contains portions of the application code runtime data 107′. If the processing unit(s) 102 a require data not already stored in the cache 102 b then a “cache miss” occurs, and that data is fetched from the system memory 103 (typically evicting some other data from the cache 102 b). The cache 102 b is generally divided into at least a code cache and a data cache. For example, when executing the application code 107, the code cache stores at least a portion of the processor instructions stored in the application code runtime data 107′ and the data cache stores at least a portion of data structures of the application code runtime data 107′. In general, the cache 102 b is divided into separate tiers/levels (e.g., layer 1, layer 2, and layer 3), with some tiers (e.g., layer 3) potentially existing separate from the processor 102. The registers 102 c are hardware based storage locations that are defined based on the instruction set architecture of the processors(s) 102.

While not expressly depicted, each of the processors(s) 102 typically include a plurality of processing units 102 a. As such, the computer system may include a plurality of different processors 102, which each includes a plurality of processing cores. In these situations, a processor's cache 102 b may include a plurality of distinct cache portions that each correspond to a different processing unit, and the registers may include distinct sets of registers that each correspond to a different processing unit. The computer system 101 can therefore execute a plurality of “threads” concurrently both at different processors 102 and/or at different processing units 102 a within each processor.

Time Travel Debugging

As mentioned previously, previous attempts at time travel debugging would execute a multiple threads of a process non-concurrently on a single processor core, or execute multiple threads non-concurrently on different processors and/or processor cores, so that each instruction is executed—and recorded—in a precise deterministic order. Additionally, previous attempts would exhaustively record changes to memory state of a process in a deterministic manner, so that every memory value is known at any given time. The embodiments herein, however, are able to execute and trace a plurality of threads concurrently, removing the requirement that each instruction to be executed and recorded in a precise order, and are able to enable replay while recording much less than a full record of instruction execution and memory state.

At a conceptual level, the embodiments herein record a trace of execution of one or more threads of a process individually on one or more processors, and record these trace(s) in trace file(s) 108 that can be used to reproduce the inputs and outputs of each processor instruction executed as part of each thread (without necessarily recording each instruction executed), that includes an approximation of the order of instruction execution across different threads, and that stores enough information to predict relevant memory values, without exhaustively recording full changes to memory state. It is noted that, while the embodiments herein can trace all the threads of a process, they may also trace only a subset of the threads of a process. Also, it is noted that the embodiments herein may trace execution of the application code 107 on physical processor(s), on virtual processor(s) such as processor that is emulated through software, and/or even in virtual machine environments (e.g., .NET from MICROSOFT CORPORATION, JAVA from ORACLE CORPORATION, and the like). As an example of tracing within virtual machine environments, recording a JAVA program may include recording what operations and memory reads a “virtual processor” of a JAVA virtual machine performs. Alternatively, recording a JAVA program could include recording both the JAVA program and the JAVA virtual machine (e.g., by recording execution of native code that “just in time” compiles the JAVA code, that executes garbage collector, etc.). In the latter situation, the time travel debugger 106 may be configured to separate replay of the different layers (i.e., the application code vs. the JAVA virtual machine code).

The embodiments herein are built upon the recognition by the inventors that processor instructions (including virtual machine “virtual processor” instructions) can generally fall into one of three categories: (1) instructions identified as “non-deterministic” as not producing predictable outputs because their outputs are not fully determined by data in general registers or memory, (2) deterministic instructions whose inputs do not depend on memory values (e.g., they depend only on processor register values, or values defined in the code itself), and (3) deterministic instructions whose inputs depend on reading values from memory. Thus, in some embodiments, reconstructing the execution of instructions can be accomplished with solutions to three corresponding challenges: (1) how to record the non-deterministic instructions that produce output not fully determined by their inputs, (2) how to reproduce the values of input registers for instructions depending on registers, and (3) how to reproduce the values of input memory for instructions depending on memory reads.

As a solution to the first challenge, of how to record “non-deterministic” instructions executed by a thread that do not produce fully predictable outputs because their outputs are not fully determined by data in general registers or memory, embodiments including storing in the trace of the thread the side-effects of execution of such instructions. As used herein, “non-deterministic” instructions include somewhat less common instructions that (i) produce non-deterministic output each time they are executed (e.g., RDTSC on INTEL processors, which writes the number of processor cycles since the last processor reset into a register), that (ii) may produce a deterministic output, but depend on inputs not tracked by the record component 106 a (e.g. debug registers, timers, etc.), and/or that (iii) produce processor specific information (e.g., CPUID on INTEL processors, which writes processor-specific data into registers). Storing the side-effects of execution of such instructions may include, for example, storing register values and/or memory values that were changed by execution of the instruction. In some architectures, such as from INTEL, processor features such as those found in Virtual Machine eXtensions (VMX) could be used to trap instructions for recording their side effects in the trace file(s) 108.

As a solution to the second challenge, of reproducing the values of input registers for deterministic instructions executed by a thread (e.g., whose inputs depend only on processor register values) is straightforward, as they are the outputs of the execution of the previous instruction(s) in the thread. Recording the execution of an entire series of processor instructions in the trace of the thread can therefore be reduced to reproducing the register values at the beginning of the series; the trace file(s) 108 need not store a record of which particular instructions executed in the series, or the intermediary register values. This is because the actual instructions are available in the application code 107 itself, and which are available at replay time. These instructions can therefore be supplied the recorded inputs (i.e., the recorded initial set of register values) during reply, to execute in the same manner as they did during the trace of the thread.

As a solution to the third challenge, of reproducing the values of input memory for deterministic instructions executed by a thread whose inputs depend on memory values, embodiments include recording in the trace of the thread the memory values that the instructions in the thread consumes (i.e., its reads)—irrespective of how the values that the instructions read were written to memory. In other words, some embodiments include recording only memory reads, but not memory writes. For example, although values may be written to memory by the current thread, by another thread (including the kernel, e.g., as part of processing an interrupt), or by a hardware device (e.g., input/output hardware 105), it is just the values that the thread's instructions read that are needed for full replay of instructions of the thread that perform reads. This is because it is that values that were read by the thread (and not necessarily all the values that were written to memory) that dictated how the thread executed. While in some embodiments, the value of each memory value read may be stored in the trace file(s) 108, other embodiments include optimizations such as prediction techniques that attempt to predict the appropriate values without necessarily recording each read. For example, in some implementations, if the predicted value is the value that was actually read from memory, then nothing needs to be recorded in the trace file(s) 108; however, if the predicted value does not match the value that was actually read then the value read is recorded in the trace file(s) 108. One such prediction technique is to predict that the next memory value read by a thread will be the same as the value previously read by the thread, as demonstrated below. Another prediction technique is to always predict that the next memory read will have a value of zero. Other example prediction techniques are also discussed later.

Additionally, since each of the threads are recorded independently from one another, the trace file(s) 108 do not need to record a strict ordering of each and every instruction executed across all threads (e.g., using a fully sequentially consistent recording model, as discussed above). However, it may be useful for later debugging to record an approximation of the order in which the instructions executed. Thus, in order to record an approximation of the order in which the instructions executed across threads, embodiments instead define or identify a “trace memory model” having defined “orderable” and “non-orderable” events Then, the record component 106 a records the execution sequence of the “orderable” events that occurred during thread execution. For example, embodiments may use a monotonically incrementing number (“MIN”) that is guaranteed not to repeat to record the sequence in which orderable events occurred across threads. In general, a trace memory model should define how threads can interact through shared memory, and their shared use of data in the memory. The trace memory model used may be a memory model defined by a programming language used to compile the application code 107 (e.g., C++ 14), or some other memory model defined for purposes of tracing (such as one defined by the time travel debugger 106).

As an example, a first trace memory model may treat as orderable only kernel calls (from user mode), traps, and exceptions. This trace memory model would have low overhead, since these operations are relatively “expensive” is their own right, they are likely tracked anyway and provide a very coarse grained overview of ordering.

A second example trace memory model may treat as orderable full fences (i.e., operations that are have both acquire & release semantics). Examples of such operations may include INTEL's “locked” instructions, kernel calls, exceptions, and traps. This memory model would provide enough ordering for nearly all cross-thread communication that happens in the process when the code uses “interlocked” types of primitives to communicate cross threads, which is common in operating such as WINDOWS from MICROSOFT CORPORATION).

A third example trace memory model may treat all acquires and releases as orderable. This memory model may be suitable for processors based ARM instruction sets, because ARM does not treat most loads and stores as acquires or releases. On other architectures, such as from INTEL (in which a majority of memory accesses are acquires or releases), this would equate to ordering almost all memory accesses.

A fourth example trace memory model may treat as orderable all memory loads. This would provide for strong ordering but may lead to decreased performance as compared to the other example memory models.

The foregoing memory models have been presented as examples only, and one of ordinary skill in the art will recognize, in view of the disclosure herein, there a vast variety of memory models may be chosen.

In view of the foregoing, FIG. 2 illustrates an example flowchart of a method 200 for recording a replay-able trace of execution of a multi-threaded process. As depicted, method 200 includes an act 201 of identifying a memory model. Act 201 may include identifying a trace memory model that defines one or more orderable events that are to be ordered across a plurality of threads of the multi-threaded process. For example, act 201 may include the record component 106 a identifying or defining a memory model such as, as examples only, treating kernel calls, traps, and exceptions as orderable; treating full fences as orderable; treating all acquires and releases as orderable; treating all memory loads as orderable; etc., as discussed above.

FIG. 2 also depicts that method 200 includes an act 202 of executing a plurality of threads concurrently. Act 202 may include executing the plurality of threads concurrently across one or more processing units of one or more processors, while observing their execution with the record component 106 a. For example, act 202 may include executing a first thread of the process on a first processing unit 102 a of a processor, while executing a second thread of the process on a second processing unit 102 a of the same processor. As another example, act 202 may include executing two threads of the process on the same processing unit 102 a of a processor that supports hyper-threading. As another example, act 202 may include executing two threads of the process on different processing units 102 a of different processors. Combinations of the foregoing are also possible.

FIG. 2 also depicts that method 200 includes an act 203 of recording a trace for each thread independently. Act 203 may include, during execution of the plurality of threads, recording a separate replay-able trace for each thread independently. As will be clear in view of examples herein after, the recorded trace for each thread stands independent from one another, except that they may include orderable events that are identified by a MIN across the threads. As illustrated, act 203 may include sub-acts that are performed by the record component 106 a for each thread, as they execute.

FIG. 2 also depicts that act 203 includes an act 204 of, for each thread, recording initial thread state. Act 204 may include the record component 106 a storing initial processor register values, for example. Other initial thread state may include the Thread Environment Block (TEB) and/or the Process Environment Block (PEB) for the first thread of a process. Recording the TEB and/or the PEB may provide useful debugging information later (e.g., thread local storage data). Other initial thread state may include the thread's execution stack, particularly if the record component 106 a is starting recording of a thread that is already executing.

FIG. 2 also depicts that act 203 may include an act 205 of recording side effects of non-deterministic instructions. Act 205 may include recording the side effects of at least one non-deterministic processor instruction executed by the thread. For example, the record component 106 a may record the side effects of nondeterministic instructions by recording any changes made by the instructions to register values.

FIG. 2 also depicts that act 203 includes an act 206 of, for each thread, recording memory reads. Act 206 may include recording at least one memory read performed by at least one processor instruction executed by the thread that takes memory as input. For example, the record component 106 a may record trace file(s) 108 that can be used to reproduce the values read from memory during replay time. This may include recording each read, or applying one or more algorithms to predict reads to reduce the number of read entries that need to be recorded in the trace file(s) 108.

FIG. 2 also depicts that act 203 includes an act 207 of, for each thread, recording orderable events. Act 207 may include recording a least one orderable event performed by the thread with a monotonically increasing number that orders the event among other orderable events across the plurality of threads. For example, the record component 106 a may record the sequence of execution of events that are orderable by the trace memory model using a MIN that applies across threads. As such, the replay component 106 b can ensure that these events are sequenced across thread during replay. One example orderable event is beginning of a trace. Others are given in connection with the examples of Tables 1 and 2 below.

As illustrated by the double-ended arrows between acts 205, 206, and 207, these acts may occur in any order, and may occur multiple times during tracing of a thread, as will become clear in connection with the following example.

When recording the trace, the record component 106 a may employ compression techniques to reduce the size of the trace file(s) 108. For example, the record component 106 a may dynamically compress the trace data prior to writing it to storage (whether that be in system memory 103 or data store 104). Alternatively, the record component 106 a could compress the trace file(s) 108 at the conclusion of a recording.

Tables 1-5 illustrate a concrete example of tracing execution of a process using the method 200. In particular, Tables 1-5 illustrate example techniques for recording the execution of a single thread of a multi-threaded process. While, for simplicity and clarity, only one thread recorded in this example, the recording techniques need not change, irrespective of how many threads there are that modify program state. Additionally, even if there were external entities (e.g., the kernel, hardware) modifying shared memory, the recording techniques would not need to change. This is because these recording techniques record what a processing unit 102 a actually sees (reads) and does when executing a thread, instead of focusing on constraining the execution to produce a fully predictable sequence of executed instructions.

Initially, Table 1 illustrates an example listing of processor instructions (e.g., from application code 107) to be executed by a processing unit 102 a as part of a thread.

TABLE 1 Processor Instruction Listing Address Instruction Description 10 Move R1 <- {Timer} Read machine timer 11 Move R2 <- [A] Read source buffer begin address 12 Move R3 <- [B] Read target buffer begin address 13 Move R4 <- [C] Read source buffer size (destina- tion buffer is at least as big) 14 Move R5 <- 0 15 Move R6 <- 0 Loop: 16 Compare R5 vs. R4 17 If not less jump to “Out:” If (R5 >= R4) exit loop {Instr. 25} 18 Move R7 <- [R2 + R5] Read from source buffer the ele- ment at “index” R5 19 ++R5 20 Compare R7 vs. 0 Is the value we just read zero? 21 If equal jump to “Loop:” If we read zero continue to next {Instr. 16} iteration 22 Move [R3 + R6] <- R7 Write the newly read value to the destination buffer 23 ++R6 24 Jump to “Loop:” {Instr. 16} Out: 25 Move R2 <- {Timer} 26 Subtract R1 <- R2 − R1

In Table 1, the “Address” column refers to a memory address (e.g., in the instruction portion of the cache 102 b) where the instruction specified in the “Instruction” column is found. These addresses are simplified to two digits in this example. In the instructions, R1-R7 refer to processor registers 102 c, and data contained in square brackets (“[ ]”) refer to a memory location (e.g., in the data portion of the cache 102 b).

Table 2 illustrates a sequence of instruction execution for the thread, including register state, and sample data that could potentially be recorded in the trace file(s) 108 to enable replay of the thread's execution.

TABLE 2 Instruction Execution Sequence ID# Addr. R1 R2 R3 R4 R5 R6 R7 Trace 0xff 0xff 0xff 0xff 0xff 0xff 0xff <Initial context> 0 10 T1 Instr: 0 <Orderable event, X> Instr: 0 <Side effects, R1 = T1, PC = 11> 1 11 ptrA Instr: 1 <Read value ptrA> 2 12 ptrB Instr: 1 <Read value ptrB> 3 13 5 Instr: 1 <Read value 5> 4 14 0 5 15 0 6 Loop: 16 7 17 8 18 5 9 19 1 10 20 11 21 12 22 13 23 1 14 24 15 Loop: 16 16 17 17 18 0 Instr: 14 <Read value 0> 18 19 2 19 20 20 21 21 Loop: 16 22 17 23 18 0 24 19 3 25 20 26 21 27 Loop: 16 28 17 29 18 2 Instr: 12 <Read value 2> 30 19 4 31 20 32 21 33 22 34 23 2 35 24 36 Loop: 16 37 17 38 18 2 39 19 5 40 20 41 21 42 22 43 23 3 44 24 45 Loop: 16 46 17 47 Out: T2 Instr: 18 <Orderable event, 25 X + N> Instr: 0 <Side effects, R2 = T2, PC = 26> 48 26 T2- T1

In Table 2, the “ID #” column refers the particular sequences of instruction execution, and the “Addr.” column indicates the instruction address (see Table 1) of the instruction executed at the ID #. While not necessarily recorded in the trace file(s) 108, columns “R1”-“R7” are included to illustrate the state changes to some processor registers as an aide in understanding the program execution. The “Trace” column indicates the type of data that may be recorded in connection with an instruction execution.

Per method 200, the record component 106 a would identify a trace memory model defining “orderable” and “non-orderable” instructions/events (act 201). This enables the record component 106 a to record sequencing (orderable) events across threads according to a MIN. Later, during replay, this enables the reply component 106 b to ensure that these orderable instructions are replayed across threads in proper order in relation to each other, and also enables the replay component 106 b to have flexibility in replaying non-orderable instructions within and across threads.

To illustrate, FIG. 3 provides an example 300 of ordering events across concurrently executing threads (threads A and B). In particular, FIG. 3 illustrates a timeline 301 of execution of thread A, and a concurrent timeline 302 of execution of thread B. These timelines 301, 302 show the relative order of execution of seven orderable events. In particular, timeline 301 shows that thread A executed orderable events 3 and 5, and timeline 302 shows that thread B executed orderable events 1, 2, 4, 6, and 7. During replay, the replay component 106 b ensures that these orderable events are replayed within their respective thread in proper order, and across the two threads in their proper order (i.e., B1=>B2=>A3=>B4=>A5=>B6=B7).

Non-orderable instructions are replayed relative these orderable instructions. For example, the replay component 106 b would replay any non-orderable events in time block 303 of thread B prior to replaying any non-orderable events in the time block 304 of thread B. Additionally, the replay component 106 b would replay the non-orderable events in time block 303 of thread B prior to replaying any non-orderable events in time block 305 of thread A. Furthermore, the replay component 106 b would replay the non-orderable events in time block 305 of thread A prior replaying any non-orderable events in time block 306 of thread B. However, the replay component 106 b may not enforce any particular ordering between replay of the non-orderable events in time block 305 of thread B and replay of the non-orderable events in time block 304 of thread B, since that ordering cannot be determined based on the orderable events alone. However, the replay component 106 b may enforce some ordering between these instructions if they were to both access shared memory, since their ordering could be determined, at least partially, based on how and when they access the shared memory (including the values accessed).

Returning to FIG. 2, method 200 would proceed to record an individual trace for each thread (act 203). Prior to executing any instructions for a given thread, the record component 106 a records initial state/context (act 204), such as the initial values of the processor registers 102 c (i.e., all 1's (0xff) for each of R1-R7, in this example).

The record component 106 a then proceeds to monitor and record execution of the thread, recording in the trace file(s) 108 appropriate instructions/events as the occur, such as the side effects of the execution of non-deterministic instructions (act 205), memory reads (act 206), and orderable events (act 207).

For example, at ID #0, the record component 106 a records execution of the instruction at address 10 (i.e., “Move R1←{Timer}” per Table 1). This instruction reads a timer, and places the value in a register (R1). In this example, assume that the chosen trace memory model (act 201) defines getting the timer as an “orderable” instruction which we should record with a MIN. As such, the record component 106 a records the sequencing (orderable) event “X” in the trace file(s) 108 (act 207). In the example, this is notated in the “Trace” column as “Instr: 0<Orderable event, X>,” meaning that zero instructions since the last data written to the trace, record the sequencing (orderable) event identified by the MIN X.

Note that the particular notation (MIN) for recording sequencing (orderable) events can be any notation (hence the use of the generic “X”), so long as it is a value that is guaranteed not to repeat within the same recording, and is monotonically incrementing (e.g., A, B, C, etc.; 1, 2, 3; etc.; 10, 20, 30, etc.). One possible option is to use a processor-provided timer value, such as the value returned by the RDTSC instruction on INTEL processors. Thus, operations that happen later than “X” will have a sequence identifier that is strictly greater than “X” no matter which thread those operations took place on.

Additionally, instruction 10 is the first category of non-deterministic instructions, which produce results that do not depend only on inputs (e.g., there is no input, and the timer value returned with be different each time the instruction is executed). As such, the record component 106 a records the side effects of its execution in the trace (act 205). In the example, this is notated in the “Trace” column as “Instr: 0<Side effects, R1=T1, PC=11>,” meaning that zero instructions since the last data written to the trace (which was “Instr: 0<Seq. event, X>”), record the new value of R1 (which is time T1), and increment and record the program counter (PC, not shown) register (i.e., to the next instruction at address 11).

While this example records updates to the PC as a side effect, some embodiments may omit doing so, since the replay component 106 b would be able to determine how far the PC should be incremented based on analysis of the instruction executed. However, recoding the PC allows “jump” instructions to be recorded as side effects, which offers the opportunity to record the execution of several instructions with a single entry to the trace file(s) 108.

At this point, the trace file(s) 108 have enough information that the replay component 106 b could set up initial thread state (e.g., set the values of R1-R7 to 0xff), could replay instruction 10 (by reproducing its side effects), and could order instruction 10 against any other instructions within this thread, or within other threads that the record component 106 a is track the ordering of that are executing concurrently.

Next, at ID #1, instruction 11 performs a read (a read the address of memory location A, and place the value in R2, see Table 1). Since this instruction reads memory, the record component 106 a records this to the trace file(s) 108 (act 206) in such a manner that at replay time the replay component 106 b can reproduce or predict the value that was read. As discussed previously, this could include the record component 106 a recording the value of every read, though there are various optimizations to reduce the amount of data that needs to be written. One approach is to predict that the value read by the current instruction is the value that was last read by the thread (and recorded in the trace file(s) 108). In this case, the trace file(s) 108 contain no previous reads for this thread, so the read needs to be recorded. In the example, this is notated as “Instr: 1<Read value ptrA>” meaning that one instruction since the last data written to the trace (i.e., “Instr: 0<Side effects, R1=T1, PC=11>”), read the address of memory location A. As indicated, this address (ptrA) would be placed by the instruction into R2.

The instructions executed at ID #'s 2 and 3 (instructions 12 and 13) also need to be recorded, since they are also reads (act 206). The data recorded in the trace file(s) 108 by the record component 106 a is similar to that which was recorded for instruction 11. For ID #2 (instruction 12) the notation “Instr: 1<Read value ptrB>” means that one instruction since the last data written to the trace, read the address of memory location B. For ID #3 (instruction 13) the notation “Instr: 1<Read value 5>” means that one instruction since the last data written to the trace, read the value 5. Note that, per the example prediction algorithm, both of these would need to be written to the trace file(s) 108, since each read produces a different value than the previous read. As indicated, the address for location B (ptrB) would be placed by instruction 12 into R2, and the value 5 would be placed by instruction 13 into R4.

For ID #'s 4 and 5, instructions 14 and 15 are deterministic, with no reads from memory, so the record component 106 a does not need to record anything in the trace file(s) 108. Similarly, for ID #6, instruction 16 is deterministic and depends only on the values of R5 and R4. No recording in the trace file(s) 108 is necessary, as those values will be reproduced by the replay component 106 b based on replay of instructions 13 and 14, together with the trace data for the instruction at ID #3.

For ID #7, instruction 17 also doesn't require any trace data to be recorded, since its behavior (to not take the jump, since the value of R5 is not less than the value of R4) is fully determined by data already recorded (or implicit) in the trace file(s) 108. For example, at replay time, the trace data for ID #3 would case the replay component 106 b to place a value of 5 in R4, and the value of zero would have been written to R5 based on replaying instruction 14 at ID #4.

For ID #8, instruction 18 is a read from memory (the memory location identified by [R2+R5]), and should therefore be considered for recording (act 206). Assume that a value of 5 was observed by the record component 106 a to have been read during execution (as indicated in column “R7”). While the record component 106 a could record this read in the trace file(s) 108 (e.g., “Instr: 5<Read value 5>”), it can avoid doing so by applying the read prediction algorithm discussed above: if the value read is the same as the value from the least read operation by the thread, do not record it. In this case, the last value read was 5 (ID #3), so the record component 106 a does not need to record anything in the trace file(s) 108 for ID #8.

For ID #'s 9-11, the record component 106 a also does not need to record anything to be able to replay instructions 19-21, since everything needed to execute these instructions is already known. For ID #12 (instruction 21) the record component 106 a also does need to record anything, since this instructions' input is only a register, and since writes to memory (i.e., the location identified by [R3+R6]) do not need to be recorded—as discussed previously, while reads from memory affect how and which instructions executed, writes do not. The record component 106 a also does not need to record anything for ID #'s 12-16 (instructions 23, 24, Loop: 16, and 17), since everything needed to execute these instructions is already known.

For ID #17, the second time instruction 18 (a read from memory) is encountered, the value of 0 is read (as indicated in column “R7”). This value is not the value that would be predicted by the record component 106 a using the sample prediction algorithm (since it is different than the last value of 5 that was read) so the record component 106 a adds it to the trace file(s) 108 per act 206 (e.g., “Instr: 14<Read value 0>,” indicating that fourteen instructions after last data logged, read the value of zero).

The record component 106 a doesn't need to add anything to the trace file(s) 108 for ID #'s 18-22 (instructions 18, 20, 21, Loop: 16, and 17). As before, the replay engine 106 b would already have enough information to reproduce the same results as record component 106 a observed. At replay, the replay component 106 b would compare the same values, take the same jumps, etc.

ID #23 is the third time instruction 18 (a read from memory) is encountered, and another 0 (as indicated in column “R7”) is read. While the record component 106 a needs to consider adding it to the trace file(s) 108 (act 206), this value was predicted by the prediction algorithm (the last read was also a 0 at ID #17), so the record component 106 a doesn't record anything into the trace file(s) 108.

Again, the record component 106 a doesn't need to record anything to the trace file(s) 108 for ID #'s 24-28 (instructions 19, 20, 21, Loop: 16, and 17), since the replay component 106 b would already have enough information to reproduce the same results.

For ID #29, the fourth time instruction 18 (a read from memory) is encountered, a value of 2 (as indicated in column “R7”) is read. This value is not the predicted value (it is different than the last value we read, which was 0) so the record component 106 a adds it to the trace file(s) 108 per act 206 (twelve instructions since the last entry, read a value of 2).

The record component 106 a also doesn't need to add anything to the trace file(s) 108 for ID #'s 30-37 (instructions 19, 20, 21, 22, 23, 24, Loop: 16, and 17). Again, the replay component 106 b would already have enough information to reproduce the same results.

ID #38 (instruction 18) is another memory read (from location [R2+R5]). As indicated in R7, a value of 2 was read, which is the same as last read at ID #29. While the record component 106 a needs to consider writing it to the trace file(s) 108 (act 206), it does not need to do so per the prediction algorithm.

The record component 106 a also doesn't need to add anything to the trace file(s) 108 for ID #'s 39-46 (instructions 19, 20, 21, 22, 23, 24, Loop: 16, and 17). Again, the replay component 106 b already has enough information to reproduce the same results the record component 106 a observed.

At ID #47, the record component 106 a observes another timer read at instruction 26. Since this is an “orderable” event per our memory model (as discussed in connection with ID #0), the record component 106 a records the sequence/order of the operation with an incremented identifier per act 207 (e.g., data stating that eighteen instructions after the last logged data, the sequencing event X+N occurred). Also, since this is a non-deterministic instruction, the record component 106 a records its side effects per act 205 (e.g., data stating that zero instructions after the last logged data, record the effects: R2=T2, and PC=26).

For ID #48, there are no reads and the instruction is deterministic, so the record component doesn't log anything in the trace file(s) 108.

Table 3 summarizes an example of the trace data that the record component 106 a may have recorded in the trace file(s) 108 as part of tracing execution of this thread.

TABLE 3 Example Trace with Prediction <Initial context (e.g., registers)> Instr: 0 <Orderable event, Id X> Instr: 0 <Side effects, R1 = T1, PC = 11> Instr: 1 <Read value ptrA> Instr: 1 <Read value ptrB> Instr: 1 <Read value 5> Instr: 14 <Read value 0> Instr: 12 <Read value 2> Instr: 18 <Orderable event, Id: X + N> Instr: 0 <Side effects, R2 = T2, PC = 26>

The replay component 106 b can later use this trace data to set up initial context (e.g., register state) and then, together with the thread's code (e.g., Table 1), execute the same instructions in the same manner that they executed at record time, by reproducing the side effects of non-deterministic instructions, and supplying memory values when needed (using knowledge of the prediction algorithm used during the recording). Additionally, the sequencing events (X and X+N) enable the instructions at ID #'s 0 and 47 to be executed in the same order relative to sequencing events in other threads as they executed during record time. Thus, the tracing mechanisms enable the tracing and replay of both individual and multiple concurrently executing threads, while recording a small amount of trace data—and much less than a fully deterministic record in the instructions executed and full memory state. Notably, in the foregoing example, the record component 106 a did not track or record when, why, or who (i.e., another thread in this process, the same thread earlier, another process, the kernel, hardware, etc.) wrote the values that were read and consumed by the code in Table 1. Nonetheless, the replay component 106 a is still enabled by the trace Table 3 to replay execution of in the exact manner that it was observed.

As one of skill in the art will recognize, in view of the disclosure herein, there are many variations on the particular manner in which the trace data may be recorded. For example, while the example trace tracks when an event took place based on an instruction count that is relative to the number of instructions executed since the previous entry into the trace, an absolute instruction count (e.g., a count starting at the beginning of the trace) could also be used. Other examples that could be used to uniquely identify each instruction executed may be based on a count of a number of CPU cycles executed (either relative to a prior entry, or as an absolute value), a number of memory access made, and/or a jump taken count together with the processor's program counter (which could be relative to the last execution discontinuity or kernel call, or absolute from a defined time). When using one more of the foregoing techniques, care may need to be taken when recording certain types of instructions, such as “repeat” instructions (e.g., REP on INTEL architectures). In particular, on some processors a repeat instruction may actually execute with the same program counter on each iteration, and thus on these processors a repeat instruction with multiple iterations may count only as one instruction. In these circumstances, the trace should include information can be used to distinguish each iteration.

Additionally, there are various mechanisms for recording and predicting the values read. As one simple example, embodiments may eliminate the prediction algorithm altogether. While this would generate a longer trace, it would also remove the restriction that the replay component 106 b be configured with the same prediction algorithm as the record component 106 a. Table 4 illustrates what the trace may look like without use of a prediction algorithm, and in which each memory read is recorded. As shown, without the prediction algorithm, the trace would include three new entries (shown with emphasis), while other entries (i.e., those following each new entry) each have an updated with instruction count that reflect count from the new entry that precedes it.

TABLE 4 Example Trace without Prediction <Initial execution context (e.g., registers)> Instr: 0 <Orderable event, Id X> Instr: 0 <Side effects, R1 = T1, PC = 11> Instr: 1 <Read value ptrA> Instr: 1 <Read value ptrB> Instr: 1 <Read value 5> Instr: 5 <Read value 5> Instr: 9 <Read value 0> Instr: 6 <Read value 0> Instr: 6 <Read value 2> Instr: 9 <Read value 2> Instr: 9 <Orderable event, Id: X + N> Instr: 0 <Side effects, R2 = T2, PC = 26>

Note that the trace file(s) 108 need not record the memory address of the values read, if it can map them based on which instruction consumed them. Thus, instructions that produce more than one read may require a means to identify which read is the one in the trace file(s) 108 (i.e., when there is only one read for that instruction), or which read is which (i.e., if there are several in the trace file(s) 108). Alternatively, the trace file(s) 108 could contain the memory address for these reads or for all reads. The trace file(s) 108 just need to include enough information for the replay component 106 b to be able to read the same values that the record component 106 a observed, and match them to the same parameters so it can produce the same results.

Additionally, events (i.e., discontinuities in code execution) may occur that are not discoverable in the code stream, such as access violations, traps, interrupts, calls to the kernel, etc. The record component 106 a also needs to record these events so that they can be replayed. For example, Table 5 illustrates an example trace that may be recorded in the trace file(s) 108 if ID #33 (instruction 22) had generated an access violation.

TABLE 5 Example Trace with Exception <Initial execution context (e.g., registers)> Instr: 0 <Orderable event, Id X> Instr: 0 <Side effects, R1 = T1, PC = 11> Instr: 1 <Read value ptrA> Instr: 1 <Read value ptrB> Instr: 1 <Read value 5> Instr: 14 <Read value 0> Instr: 12 <Read value 2> Instr: 4 <Exception record> Instr: 0 <Exception context> <end-of-trace>

In particular, the trace contains “Instr. 4<Exception record>,” signaling that an exception occurred and that the exception happened 4 instructions after the last entry into the trace, and “Instr: 0<Exception context>,” which resets the instruction count to zero in connection with restarting execution after the exception and recording any appropriate state. While, for clarity, Table 5 shows separate records for signaling the occurrence of an exception and for recording the exception context, they could be in the same entry. Setting the instruction count to zero signals to the replay component 106 b that the two entries apply to the same instruction. Now, since the trace files(s) 108 contain an entry for an exception, the trace has a precise location for such an exception. This enables the replay component 106 b to raise the exception at the same point in execution that it was observed a record time. This is important, because exceptions are not inferable by looking at the code stream (since their occurrence is often based on data not present in the code stream).

As mentioned above, various mechanisms for tracing the values read may be employed by the record component 106 a, such as predicting that the value that will be read equals the last value read, and recording the read in the trace file(s) 108 if the values are different. One alternative approach to extend this prediction algorithm using a cache, so that that the record component 106 a predicts that the most likely value to be read from a particular address is the last value that was read from or written to that address. Thus, this approach needs to maintain a cache of the memory range of a process, and use the cache to track memory reads and writes.

In order to avoid overhead of this approach (i.e., keeping a cache that tracks of the last value placed in the entire memory range of a program), one refinement is for the record component 106 a to create a “shadow copy” of a much smaller amount of memory than the full memory that is addressed (as discussed below). Then, for each read observed, the record component 106 a compares the value the instruction read with that of the matching position at the shadow copy. If the values are the same, there is no need for the record component 106 a to save a record of the read in the trace file(s) 108. If the values are different, then the record component 106 a records the value into the trace file(s) 108. The record component 106 a can update the shadow copy on reads and/or on writes to increase the likelihood of predicting the value correctly the next time the memory location is read.

In some embodiments, the size of the shadow copy could be defined as 2{circumflex over ( )}N addresses. Then, to match an address to its shadow copy, the record component 106 a takes the low N bits of the memory address (i.e., where N is the power of 2 that determined the size of the shadow copy). For example, with a value of N=16, the shadow copy would be 64 k (2{circumflex over ( )}16) addresses, and the record component 106 a takes the low 16 bits of each memory address, and compares them with that offset in the shadow copy. In some embodiments, the shadow copy is initialized with all zeros. Zeros may be chosen because it is an unambiguous value, and because zeroes are read quite frequently from memory. However, other choices of initial values may alternatively be used depending on the implementation.

FIG. 4 illustrates an example 400 of use of a shadow copy, according to some embodiments. FIG. 4 represents addressable memory 401 of a process. For simplicity in illustration, the process in the example 400 only can address 2{circumflex over ( )}4 (sixteen) memory locations, which is only a fraction of what a typical process would be able to address on contemporary computers (which would typically be on the order of 2{circumflex over ( )}32, 2{circumflex over ( )}64, or more, memory locations). In the representation of the addressable memory 401, the address column specifies the binary address of each memory location (i.e., binary addresses 0000-1111), and the value column represents a location for data to be stored at each memory location. In accordance with the shadow copy described above, FIG. 4 also represents a corresponding shadow copy 402 of the addressable memory 401 that may be kept by the record component 106 a during tracing of a thread. In the example, the value of N equals two, so the shadow copy 402 stores 2{circumflex over ( )}2 (four) memory locations (i.e., binary addresses 00-11).

Any time the record component 106 a detects a read from the addressable memory 401, the record component 106 a compares the value read from the addressable memory 401 with the corresponding location in the shadow copy 402. For example, when any of memory locations 401 a, 401 b, 401 c, or 401 d are read (i.e., binary addresses 0000, 0100, 1000, or 1100), the record component 106 a compares the value read from that location to the value in location 402 a of the shadow copy (i.e., binary address 00, because the last N digits of each of the foregoing memory addresses is 00). If the values match, then the read need not be recorded in the trace file(s) 108. If the values do not match, the record component 106 a records the read in the trace file(s) 108, and updates the shadow copy with the new value.

Even though each location in the shadow copy 402 represents multiple locations in the addressable memory 402 (four, in this case), it is noted that most programs are likely to perform multiple reads from and/or writes to the same location in the addressable memory 402 (e.g., to read or update a variable value), so there are likely to be a high number of reads that are predicted by the shadow copy 402. In some embodiments, the record component 106 a may also update the shadow copy 402 when writes occur, which may further increase the likelihood of a correct prediction.

In some embodiments, rather than tracking memory reads at the finely-grained level of memory addresses, the record component 106 a may track reads across multiple threads at the memory page level (e.g., based on page tables). This embodiment is built on the recognition that memory pages are restricted, such that each page of memory can either (i) be written to by one thread, with no other thread having read or write access to the page; or (ii) be read by as many threads as need, but no thread can write to it. Embodiments may therefore group threads into families such that, during record time, the threads within one family always execute non-concurrently among each other (i.e., no two threads of the same family can execute at the same time). Then, the restrictions mentioned above are applied across the thread families—such that, other than concurrent page access, threads of different thread families can run concurrent to each other. If a thread family “owns” a page for writing, then no other thread family can have access to it; however, one or more thread families can share a page for reading.

When a thread family accesses a page for either reading or writing it needs to know the entire contents of the page. If the page was produced/written to by a thread in a thread family that is already being recorded, the record component 106 a is aware of the page's contents already. Thus, in some embodiments, the record component 106 a only puts information on the trace identifying the point in the recording that the writing thread released the page. For pages that have been produced/written to by external entities (e.g., the kernel, threads not being traced, a hardware component, etc.) strategies for recording the page so that it is available at replay time may include the record component 106 a recording the entire page, or the record component 106 a recording a compressed version of the page. If the page has been previously recorded, another strategy includes the record component 106 a storing only a difference in page values between the current version of the page and the prior recording.

As indicated previously, when debugging code traced by the record component 106 a, a breakpoint in the “backwards” direction is reached by the replay component 106 b replaying the trace file(s) 108 from a time prior to the breakpoint until the breakpoint is reached (e.g., the last time that breakpoint hits that is before where the debugger is currently analyzing the code stream). Using the traces described above, this would mean replaying the trace from the beginning of the trace file(s) 108. While this may be acceptable for smaller traces, it could be time-consuming and inefficient for larger traces. In order to improve the performance of replay, in some embodiments, the record component 106 a records a plurality of “key frames” in the trace files 108. Then, the key frames are used by the replay component 106 b to more granularly “zero in” on the breakpoint. For example, in some implementations the replay component 106 may iteratively “go back” an increasing number of key frames (e.g., doubling the number of key frames each iteration) until the chosen break point is reached. To illustrate, the replay component may go back one key frame and try to hit the breakpoint, if that fails it may go back two key frames and try to hit the breakpoint, if that fails it may go back four key frames and try to hit the breakpoint, etc.

Generally, key frames include enough information that the replay component 106 b can replay execution starting at the key frame, generally without regard for what came prior to the key frame in the trace. The exact timing of recording key frames, and data collected, may vary based on implementation. For example, at periodic intervals (e.g., based on the number of instructions executed, based on processor cycles, based on elapsed clock time, based on the occurrence of “orderable” events according to the trace memory model, etc.) the record component 106 a may record in the trace files(s) 108 for each thread a key frame enough information to begin replay of the trace of each thread from the key frame. This information may include the state of the hardware registers at the time that that the key frame was taken. This information also may include any information needed to put the memory prediction tactic to a known state, so that it can reproduce reads starting at the key frame (e.g., by recording memory snapshot(s), shadow copy(s), the last value(s) read, etc.). In some embodiments, key frames are usable to enable gaps in a trace. For example, if tracing is stopped for any reason this can be noted in the trace file(s) 108 (e.g., by inserting a notation that tracing was stopped and an appropriately formatted key frame), and tracing can then be restarted later from that point in the trace file(s) 108.

In some embodiments, some key frames may include information that may not be strictly necessary to enable replay at the key frame, but that nonetheless proves useful during debugging (e.g., to help the time travel debugger 106 consume the data generated during replay, and present it in a useful form). This information may include, for example, a copy of the one or more portions of the thread's stack, a copy of one or more portions of memory, the thread's TEB, the process' PEB, the identity of loaded modules and their headers, etc. In some embodiments, key frames that include this additional information (e.g., “full” key frames) may generated and stored less frequently than regular key frames (e.g., “lightweight” key frames). The frequency of the gathering of lightweight key frames and/or full key frames, and the particular data collected in each, may be user-configurable at record time.

In some embodiments, recording “full” key frames also can be useful for features such as a reusable ring buffer, which is discussed below in connection with FIG. 5. Recording “lightweight” key frames also enables the replay component 106 b to parallelize replay; each thread trace following a key frame can be replayed independently from other threads, and hence in parallel. Additionally, key frames can enable the replay component 106 b to replay different segments of the same thread trace in parallel. For example, doing so may be useful more quickly hit a breakpoint using the time-travel debugger 106. In some embodiments, the recording of “full” key frames is coordinated across threads (i.e., the record component 106 a records a full key frame for each thread of a process at approximately the same time), while “lightweight” key frames are recorded for each thread independent of other threads (i.e., the record component 106 a records lightweight key frames for each thread which it is convenient or otherwise makes sense for that thread). Adjusting the conditions for recording different types of key frames provides flexibility to balance trace size, replay-ability, record performance, and replay performance.

Some embodiments may include the use of “snapshots,” which comprise a full copy of relevant memory of a process. For example, the record component 106 a may take an initial snapshot of a process' memory when beginning a trace of that process. This enables the replay component 106 b to provide a user of the time-travel debugger 106 with the values of all of the memory locations used by the process, instead of only those that were observed to be accessed during recording.

In some embodiments, the trace file(s) include information that is usable to by the replay component 106 b validate that the state of the program at replay indeed matches the program state that existed during recording. For example, the record component 106 may include in the trace file(s) 108 periodic information such as copy register data and/or a computed hash of the register data. This information may be included in key frames, may be periodically included with standard trace entries, and/or may be included based on a number of instructions executed (e.g., placed in the trace every X instructions), etc. During replay, the replay component 106 b can compare the recorded register data (and/or the computed hash) at corresponding points in the execution state data generated during replay to ensure the execution state is the same (i.e., if the register data during replay and/or a computed hash of this data match, the execution state is likely the same; if they do not match, the execution state has deviated).

As alluded to previously, some embodiments include recording trace file(s) comprising a “ring buffer” of limited capacity. In particular, a ring buffer records only a trailing portion of program execution (e.g., the last N minutes, hours, days, etc. of execution). In concept, a ring buffer adds new trace data to the front/top of the trace, and removes old trace data from the back/bottom of the trace. For example, some applications may run for days, weeks, or even months/years before a programming bug manifests. In such situations, it may be impractical (e.g., in terms of the amount of disk space used) and unnecessary to trace a full history of program execution, even with the compactness of the trace files recorded by the disclosed embodiments. Additionally, use of a ring buffer could potentially allow the entire trace file(s) 108 to be stored in RAM, which can greatly reduce disk I/O and improve performance (both during record and replay).

When implementing a ring buffer, embodiments may track both “permanent” trace information and “temporary” trace information, with the “temporary” information being stored in the ring buffer. Examples of “permanent” trace information may include general information, such as the identity of loaded modules, the identity of the process being recorded, etc.

FIG. 5 illustrates an example 500 of a reusable ring buffer 501 according to one or more embodiments. In the example, each clear rectangle in the ring buffer 501 represents a standard trace entry in the ring buffer 501 (e.g., such as the entries of Table 3 above). Each shaded rectangle (e.g., 504 a, 504 b, 504 c, 504 d, 504 e) represents a key frame. The frequency of key frames, and the number of entries between key frames, will vary based on implementation. As indicated by the arrow 502 and the dashed entries it overlays, new entries (both standard entries and key frames) are added to one end of the buffer. As indicated by the arrow 503 and the dashed entries it overlays, the oldest existing entries (both standard entries and key frames) are removed from the other end of the buffer. Entries can be added/removed on a one-by one basis, or in chucks (e.g., based elapsed time, a number of entries, the occurrence of a key frame, etc.). The overall size of the buffer is configurable based on how long the desired length of the trailing period of program execution. To replay from the ring buffer 501, the replay component 106 b initializes state data using a desired key frame, and then replays program execution from there.

As alluded to previously, the key frames of the ring buffer 501 may comprise “full” key frames, which enables not only replay by the replay component 106 b from each key frame on (e.g., using register values stored in the key frame), but also the use of additional debugging features from each key frame on (e.g., using additional information such as a thread's TEB, data caches, etc.). However, the key frames of the ring buffer 501 may also comprise “lightweight” key frames—either exclusively or in addition to “full” key frames.

The number of ring buffers used during recording may vary. For example, some embodiments may use a separate ring buffer per-thread (i.e., each thread is allocated a number of memory pages for recording trace data), while other embodiments may use a single ring buffer to record multiple threads. When using a single ring buffer, a trace of each thread is still recorded separately, but the threads record to a shared pool of memory pages.

In the second embodiment (using single ring buffer to trace a plurality of threads), each thread may obtain one page from a pool of pages allocated to the ring buffer, and start filling it with trace data. Once a thread's page is full, the thread can allocate another page from the pool. When adding key frames, some embodiments attempt to add them at approximately the same time for each of the threads. The key frames may then be used to assign a “generation” to the recordings. For example, data recorded prior to a first key frames may be “generation one” recordings, and data recorded between the first key frames and a second key frames may be “generation two” recordings. When the pages in the pool have been exhausted, the pages associated with the oldest generation of recordings (e.g., generation 1) may be released to be re-used for future recordings.

While the forgoing disclosure has focused primarily on recording to the trace file(s) 108 information usable to replay execution of code, that there are many other types of data that may be helpful for the record component 106 a to write into the trace file(s). Examples have already been given of writing key frames and additional debugging information to the trace. Other types of information that the trace my tagged with may include timing information, performance counters (e.g., cache misses, branch miss-predicts, etc.) and records of events that do not directly impact replay of the trace—but that nonetheless may help with synchronization (e.g., embedding data capturing when a user interface was captured, so this can be reproduced at replay time). Furthermore, when user mode code is being traced, the record component 106 a could tag the trace file(s) 108 with information such as: (i) when a user mode thread is scheduled in or out, (ii) when a user mode thread is suspended, (iii) when a user switched focus on an application be traced, (iv) a record of an messages the application received, (v) when a user mode process caused a page fault, etc. One of ordinary skill in the art will recognize, in view of the disclosure herein, that the particular manner for recording any of the foregoing may vary based on implementation.

The time-machine debugger 106 may be implemented as a software component in various forms. For example, at least one or more portions (e.g., the record component) of the time-machine debugger 106 may be implemented as a code portion that is injected into runtime memory of the process being recorded (i.e., “instrumenting” the processes being recorded), as an operating system kernel component, as part of a full machine emulator (e.g., BOCHS, Quick Emulator (QEMU), etc.), and/or as part of a hypervisor (e.g., HYPER-V from MICROSOFT, XEN on LINUX, etc.). When implemented as part of an emulator or hypervisor, the time-machine debugger 106 may be enabled to trace the execution of an entire operating system. Thus, the time-machine debugger 106 can trace execution of user mode code (e.g., when implemented as injected code or as part of a kernel), and/or trace execution of kernel mode code—and even an entire operating system (e.g., when implemented as part of a hypervisor or emulator).

Processor Cache Based Implementation

While the time-machine debugger 106 may be implemented entirely in software, some embodiments include a hardware cache-based recording model that can further decrease the overhead associated with recording execution of a program. As before, this model is built upon the general principle that the record component 106 a needs to create a record (i.e., trace file(s) 108) that enables the replay component 106 b to replay each instruction executed at record time in proper order, and in a manner such that each instruction produces the same outputs that it did at record time. As is clear in view of the disclosure above, a significant component of the trace file(s) 108 comprises data usable to reproduce memory reads at replay time. As discussed above, embodiments of recording such data can include recording each value read, using a prediction algorithm to anticipate the values read, using shadow copies of memory, recording memory pages and/or page table entries, etc.

Embodiments of the hardware cache-based model for tracing (including recording/reproducing memory reads) are built upon an observation that the processor 102 (including the cache 102 b) form a semi- or quasi-closed system. To further illustrate, FIG. 6 illustrates an example computer architecture 600 for processor cache based tracing, which includes a processor 601 and system memory 608, which may map to the processor(s) 102 and system memory 103 of FIG. 1.

At a conceptual level, once data is loaded into the cache 603, the processor 601 can run by itself—without any input—as a semi- or quasi-closed system for bursts of time. In particular, during program execution each processing unit 602 executes instructions from a code cache 604 section of the cache 603 using data stored a data cache 605 portion of the cache 605 and using the registers 607. For example, FIG. 6 illustrates that the code cache 604 includes a plurality of storage locations 604 a-604 n (e.g., cache lines) for storing program code, and that the data cache 605 includes a plurality of storage locations 605 a-605 n (e.g., cache lines) for storing data. As discussed previously in connection with FIG. 1, a cache may include a plurality of layers (e.g., level 1, level 2, and level 3, etc.). While the cache 605 is depicted for simplicity in description as being within the processor 601, it will be appreciated that one or more portions of the cache 605 (e.g., level 3 cache) may actually exist outside of the processor 106.

When the processing unit 602 needs some influx of information (e.g., because it needs code or data not already in the cache 603), a “cache miss” occurs and that information is brought into the cache 603 from an appropriate storage location (e.g., 608 a-608 n) of the system memory 608. For example, if a data cache miss occurs when an instruction performs a memory operation at the memory address corresponding to location 608 a (containing program runtime data), that memory (i.e., the address and the data stored at the address) is brought into one of the storage locations (e.g., location 605 a) of the data cache 605. In another example, if a code cache miss occurs when an instruction performs a memory operation at the memory address corresponding to location 608 b (containing program code); that memory (i.e., that address and the data stored at the address) is brought into one of the storage locations (e.g., location 605 a) of the code cache 604. When new data is imported to the cache 602, it may replace information already in the cache 603. In this case the old information is evicted back to the it proper address in the system memory 608. The processing unit 602 then continues execution using the new information in the cache 603 until another cache miss occurs and new information is again brought into the cache 603.

Thus, embodiments of the hardware cache-based model for recording/reproducing memory reads rely on the realization that, except for accesses to un-cached memory (e.g., reads to hardware components and un-cacheable memory, as discussed later), all the memory accesses that a process/thread performs during execution are performed through the processor cache 603. As a result, rather than creating record (e.g., a record of each read, a shadow copy, etc.) that can reproduce each individual memory read, as above, the record component 106 a can instead record (i) the data that is brought into the cache 603 (i.e., the memory address and the data stored at that address), and (ii) any reads to un-cached memory.

Since the processor 102 can be viewed as a semi- or quasi-closed system, the execution stream within the processor that occurred at record time can be replicated by the replay component 106 b using an emulator that emulates the processor and its cache system. The emulator is configured to produce the same results at replay time that occurred during record time, when the emulator is given the same inputs by the replay component 106 b that occurred at record time. The emulator need not be a precise CPU emulator—so long as it emulates instruction execution (e.g., their side effects), it need not match timings, pipeline behaviors, etc. of a physical processor. Thus, recording program execution can be reduced to recording (i) a replica of the influx of data into the system (e.g., data brought into the cache 603 based on cache misses, and un-cached reads), (ii) the data directing the replay component 106 b how/when to apply to each input at the right time (e.g., using a count of instructions executed), and (iii) data describing the system to be emulated (i.e., the processor 601, including its cache 603). This enables the time-travel debugger 106 to model the processor 102 as a linear execution machine when recording a trace—without needing to record internal parallelism or pipelining of instruction execution within the processor 102, and without needing to preserve a record the particular timing of execution of each instruction within the processor 102.

As a general overview, the hardware cache-based model for tracing a thread begins, similar to the techniques described above, by saving the processor register values into the trace. Additionally, this model begins by ensuring that appropriate portions of the processor cache 603 for the thread is empty. As discussed below, the record component 106 a records data imported to the data cache 605, and may also record data imported to the code cache 604. As such, the data cache 605 needs to be cleared at the beginning of a trace, and the code cache 604 need only be cleared if imports to the code cache 604 are being recorded. Then, at least a portion of the code of the thread is brought into the code cache 604 (e.g., by the processor executing a “cache miss” based on a memory address of the requested code and, if imports to the code cache 604 are being recorded, storing the imported cache line in the trace files(s) 108), and the processing unit 602 begins executing the processor instructions in the code cache 604.

When the code performs its first memory operation (e.g., a read or a write to a memory address in the system memory 608), a “cache miss” occurs, since the data cache 605 is empty and thus does not contain a copy of the memory at the address being accessed. As such, the correct portion of system memory 608 is brought into and stored in a cache line in the data cache 605. For example, if the memory operation was addressed to a memory address at location 608 a in the system memory 608, the data at memory location 608 a is written to a line in the data cache (e.g., location 605 a). Since data has been brought into the cache 603, the record component 106 a records this data (i.e., the address and the data that address) to the trace file(s) 108.

After this point, future memory accesses either bring new data into the cache (and hence are recorded by the record component 106 a into the trace file(s) 108) or are be performed against data that has already been brought into the cache (e.g., they may read from or write to a cache line in the data cache 605). Subsequent reads to data already in the cache do not need to be recorded. Similar to the techniques described above in connection with FIGS. 1-5, the record component 106 a need not track writes to data in the cache, since these writes can be reproduced by executing the instructions with the recorded initial state, and by reproducing the side effects of non-deterministic instructions.

Assuming that the replay component 106 b has access to the thread's original code, and that the execution was un-interrupted (e.g., there were no exceptions) at record time, then if the replay component 106 b starts with an empty cache and the recorded register values, the replay component 106 b can emulate execution by the processor 601, including bringing appropriate data into the cache 603 at appropriate times, and reproducing the side effects of non-deterministic instructions at appropriate times.

Thus, like the techniques discussed above in connection with FIGS. 1-5, when recording using this cache-based model the record component 106 a still records in the trace file(s) 108 the side effects of non-deterministic instructions that do not have their output determined exclusively by their input values. Additionally, in some embodiments, the record component 106 a still chooses a trace memory model and records in the trace file(s) 108 orderable events performed by the thread with a monotonically increasing number that orders these events across threads.

Additionally, as discussed in more detail later, in some embodiments the record component 106 a traces changes in flow of control of the thread that cannot be determined by the code of the thread alone. For example, changes in flow of control may occur due to interrupts. These may include, for example, Asynchronous Procedure Calls (“APCs”), calls from kernel mode, etc.

Furthermore, in some embodiments the record component 106 a traces only data cache 605 misses, while in other embodiments the record component 106 a traces both data cache 605 misses and code cache 604 misses. In particular, if a thread is executing only non-dynamic code, then only cache lines imported into the data cache 605 need to be traced, since all the code that needs to be executed is available at replay time. However, if a thread includes dynamic-code support, then cache lines imported into the code cache 605 also need to be traced.

Still further, in some embodiments the record component 106 a traces which instructions perform memory reads from un-cached/un-cacheable memory individually, since there is no cache miss to track these reads. Example of an un-cached/un-cacheable read is a read from a hardware device, or a read from memory that is otherwise considered un-cacheable by the processor 601 and/or operating system.

FIG. 7 illustrates a flow chart of an example method 700 for recording a replay-able trace of execution of an executable entity using cache data. As depicted, method 700 includes an act 701 of executing one or more threads concurrently. Act 701 may include executing one or more threads (e.g., user-mode threads, kernel threads, etc.) of an executable entity (e.g., process, kernel, hypervisor, etc.) across one or more processing units of one or more processors, while observing their execution with the record component 106 a. For example, act 701 may include executing a first thread on a first processing unit 602 of a processor 601, while potentially executing a second thread on a second processing unit 602 of the same processor 601. As another example, act 701 may include executing two threads on the same processing unit 602 of a processor 601 that supports hyper-threading. As another example, act 701 may include executing two threads on different processing units 602 of different processors 601. Combinations of the foregoing are also possible.

FIG. 7 also depicts that method 700 includes an act 702 of recording a separate trace for each thread independently. Act 702 may include, during execution of the one or more threads, recording a separate replay-able trace for each thread independently. Thus, as illustrated, act 702 may include sub-acts that are performed by the record component 106 a for each thread, as they execute.

FIG. 7 also depicts that act 702 includes an act 703 of, for each thread, recording initial state. Act 703 may include recording initial processor register state for the thread. For example, the record component 106 a may record the state of registers 607 corresponding to the processing unit 602 upon which the thread is executing. Initial state may also include additional information, such as a snapshot of memory, stack information, the thread's TEB, the process' PEB, etc.

FIG. 7 also depicts that act 702 includes an act 704 of, for each thread, recording imported lines of cache data. Act 704 may include, upon detecting a processor data cache miss based on execution of the thread, recording at least one line of cache data imported into the processor data cache in response to the processor data cache miss. For example, during execution of instructions in the code cache 604, one of those instructions may perform a memory operation on a particular address in the system memory 103 that is not already in the data cache 605. As such, a “cache miss” occurs and the data at that address is imported into the data cache 605 by the processor 601. The record component 106 a creates a record of that data in the trace file(s) 108. For example, if the memory address at location 608 a is imported to cache line 605 a, then the record component 106 a records the identity of memory address, and the data it contains, in the trace file(s) 108. If the thread executes dynamic code, then a cache miss may also occur with respect to loading instructions into the processor's code cache 604. As such, act 704 may also include recording at least one line of cache data imported into the processor code cache 640 in response to a processor code cache miss.

FIG. 7 also depicts that act 702 may also include an act 705 of, for each thread, recording un-cached reads. Act 705 may include recording at least one un-cached read based on execution of the thread. For example, during execution of instructions in the code cache 604, one of those instructions may perform a memory read from a memory address of a hardware device, or from a portion of the system memory 608 that is considered un-cacheable. Since there is no cache miss in this situation, the record component 106 a records value read in the trace files(s) 108 in reference to this instruction. As illustrated by the double-ended arrows between acts 704 and 705, these acts may occur in any order, and may occur multiple times during tracing of a thread.

As discussed above, the trace file(s) 108 may record when events took place using a variety of techniques (e.g., using instruction counts, CPU cycles, jump taken count together with program counter, memory access, etc.). In some embodiments it may be advantageous to use instruction counts (relative or absolute) to identify when events took place because doing so can remove timing considerations during replay. For example, for purposes of replay it may not matter how long it took the underlying hardware to serve the cache miss at record time; it may only matter that the record component 106 a records that memory address “X” had value “Y”, and that information made it into the cache 603 in time for instruction “Z” to be handled. This can significantly simplify what it takes for the replay component 106 b to replay the trace with precision, since there is no need to produce accurate timings. This approach also offers a choice of including into the trace file(s) 108 all of the cache misses, or only those that are actually consumed by the processing units 602. Thus, for example, speculative reads from the system memory 108 by the processing units 602 as part of trying to anticipate the next instructions that will be executed don't need to be traced. However, as mentioned above, in other embodiments the record component 106 a may record timing information in the trace file(s) 108. Doing so can enable the replay component 106 b to expose this timing at replay time, if desired.

Notably, if the trace file(s) 108 map every cache entry to the instruction that caused it to be brought into the processor 601, the trace file(s) 108 do not need to capture any information when a cache line is evicted from the cache 603 back to the system memory 608. This is because if the thread's code ever needs this data from system memory 608 again, it will be re-imported by the processor 601 into the cache 603 at that time. In this situation, the record component 106 a can record this re-importing of the data as a new entry into the trace file(s) 108.

As mentioned previously, in some embodiments the record component 106 a traces changes in flow of control of the thread that cannot be determined by the code of the thread alone. For example, when recording user mode code there may be extra inputs to trace, since the operating system kernel can interrupt the user mode code and thus become an external source of data. For example, when some types of exceptions happen they are handled by the kernel first, and then eventually the control is returned into user mode—that discontinuity is an input into the system. Additionally, when a kernel call is made that doesn't “return” to the instruction after the system call, this is also a discontinuity into the system. Furthermore, when the kernel changes processor registers before returning control to the user mode code, that is also input into the system. Thus, the record component 106 a creates a record of these discontinuities in the trace files(s) 108, so that the replay component 106 b can reproduce their side effects at replay time. Similarly, when recording kernel mode code (e.g., with a hypervisor) other external inputs (e.g., traps, interrupts, etc.) may occur, and the record component 106 a can create a record of these discontinuities in the trace file(s).

In some embodiments, these discontinuities are recorded in the trace file(s) 108 as an influx of information. The particular manner for recording these discontinuities can vary, so long as the trace file(s) 108 contain all of the inputs into the code being recorded to account for the discontinuities. For example, when returning to user mode from kernel mode (e.g., when user mode code is being recorded) the trace files(s) 108 could contain the set of registers that have been changed by the kernel (or all registers). In another example, the trace file(s) include the identity of a continuation instruction's address after a system call. In yet another example, the record component 106 a could flush the processor cache 602 when returning to user mode, log all valid cache entries, and/or log the entries only if/when they are used. Similarly, when recording kernel mode code, the trace file(s) can include a record of the continuation instruction after a trap/interrupt, any changes made by the trap/interrupt, etc.

In some embodiments, the record component 106 a and replay component 106 b are configured to trace and emulate the Translation Lookaside Buffer (“TLB”) of a processor, such as TLB 606 in FIG. 6. In particular, it is noted that processor caches 603 are sometimes based on memory physical address of the system memory 608, while code often references memory virtual addresses that are presented by the kernel as an abstraction to threads/processes. Entries (e.g., 606 a-606 n) in the TLB 606 store some recent translations between virtual addresses and physical addresses. Thus, in some embodiments, the record component 106 a records each new entry in TLB 606 into the trace files(s), which provides all of the data needed for the replay component 106 b to perform the translation at replay time. As with data cache 605, the record component 106 a need not records any evictions from the TLB 606.

Tracing the TLB 606 entries also allows provides several other benefits. For example, the TLB 606 enables the record component 106 a to know which memory pages are un-cached or un-available, so that reads to these pages can be logged (e.g., act 706). Also, the TLB 606 enables the record component 106 a to account for situations in which two (or more) virtual addresses map to the same physical address. For example, if the cache 603 evicts a physical address entry based on first virtual address, and then the thread accesses an overlapping physical address via a different virtual address, the record component 106 a use the TLB 606 to determine that it needs to log the access as part of a cache miss.

Some embodiments include a hardware-assisted model that can further reduce the performance impact of cache-based tracing. As indicated earlier, recording a trace begins with an empty cache 603 (and thus the cache 603 is flushed). Furthermore, if there are changes in flow of control (e.g., due to interrupts), then the cache 603 may also be flushed as part of a transition from non-recording (e.g., while in kernel mode) to recording (e.g., when execution has transitioned back to user mode). However, it is noted that flushing the processor cache 603 can be computationally expensive. Thus, embodiments include a hardware modification to the processor 601 that can prevent the need to flush the cache 603 every time the processor 601 transitions from non-recording to recording. These examples reference setting/clearing bits. It will be appreciated that, depending on the implementation, a bit may be considered to be “set” with either a one or a zero, and be “cleared” by toggling it to the opposite value.

Some embodiments extend each cache line entry (e.g., 604 a-604 n of the code cache 604 and/or 605 a-605 n of the data cache 605) with one or more additional bits that can be used to signal status of the cache line. For example, one bit may be set (e.g., to one) to indicate that the cache line has already been recorded into the trace file(s) 108. Then, instead of flushing the cache on a transition, the processor 601 only needs to toggle (e.g., to zero) these bits on the cache lines. Later, if the thread's code later consumes a cache line with the bit not set, then the entry needs to be stored into the trace, as if it was a cache miss. Setting and unsetting this bit also enables the record component 106 a to refrain from tracing any speculative memory accesses made by the processor 601 until it knows that the thread's code has indeed consumed those access.

One or more bits that signal status of each cache line may be usable in other ways as well. For example, suppose the record component 106 a is recording user mode code, and such code calls into the kernel to then come back into user mode. In this situation, instead of clearing each cache line bit when the processor 601 returns to user mode, the processor 601 could instead clear the bit only on the cache lines that the kernel mode code modified—and leave the bit set on any cache lines that were unmodified. This further reduces the amount of entries the record component 106 a needs to add to the trace file(s) 108 when returning from the kernel. However, this technique may not apply to all kernel-to user-mode transitions. For example, if the kernel just switched from a thread on another process into a thread we are recording, the bit should be cleared across all cache entries.

Notably, the foregoing concepts are usable in environments in which hyper-threading is used (i.e., multiple hardware threads are executed on the same processing unit/core). Many processors have exclusive caches for each core (e.g., each core may have its own layer-1 and layer-2 cache), and also provide a shared cache for all the cores (e.g., a layer-3 cache). Thus, when hyper-threading is in use, multiple hardware threads (e.g., “thread 1” and “thread 2”) executing on a core share the same exclusive cache (e.g., layer-1, layer 2) for that core, so the processor tags each cache line used by these threads with which thread it is associated with.

In some embodiments, one or more bits may be added to each cache line in the shared cache which signal whether the cache line has actually been modified by a thread. For example, suppose that “thread 1” is being traced and execution switches to “thread 2” on the same core. If “thread 2” accesses a cache line in that core's exclusive cache that was assigned to “thread 1,” a bit may be toggled only if “thread 2” has modified the cache line. Then, when execution switches back to “thread 1” and “thread 1” accesses this same cache line, this line need not be recorded to the trace if “thread 2” did not toggle the bit—since the contents of the cache line has not changed since “thread 1” last accessed it. The foregoing may also be applied to shared caches. For example, each cache line in layer-3 cache could include a bit for each thread it services, which indicates whether the thread has already “recorded” the current value in the cache line. For example, each thread may set its bit to one when consuming the line, and sets all other values to zero when writing to the line.

In some embodiments, the trace file(s) 108 may record entries out-of-order from the order they executed at record time. For example, suppose that entries are recorded based on the number of instructions since the last discontinuity (including kernel call) in a thread. In this situation, the entries between two discontinuities could be re-ordered without loss of information. In some embodiments, doing so may enable faster recording, since optimizations to memory access by be made by the processor. For example, if a processor executes a sequence of instructions (e.g., A, B, and C) that result in an entry to the trace file(s) 108, but that have no dependencies between them, then the order in which they are executed is irrelevant at replay time. If instruction A access data that is not already in the cache 603, then the processor 601 accesses system memory 608 at the cost of many processor cycles; but instructions B and C access data already in the cache 603, then they can be executed quickly. However, if instructions are required to be recorded in-order in the trace file(s) 108, the record of execution of instructions B and C must be held (e.g., in memory resources of the processors) until execution of the instruction A has finished. By contrast, if instructions are permitted to be recorded out-of-order, then instructions B and C can be written to the trace file(s) 108 prior to the completion of instruction A, freeing up those resources.

Accordingly, the foregoing embodiments provide new techniques for recording and replaying traces for time travel debugging that produce orders-of-magnitude performance improvements over prior attempts, that enable recording of multi-threaded programs whose threads freely run concurrently across multiple processing units, and that produce trace files with orders of magnitude size reduction over the trace files of prior attempts, among other things. Such improvements greatly reduce the amount of computing resources (e.g., memory, processor time, storage space) needed to trace and replay software. As such, the embodiments herein are usable in real-world production environments, which greatly enhances the availability and utility of time travel debugging.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the described features or acts described above, or the order of the acts described above. Rather, the described features and acts are disclosed as example forms of implementing the claims.

The present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope. 

What is claimed:
 1. A computer system comprising: one or more processors; and one or more computer-readable media having stored thereon computer-executable instructions that are executable by the one or more processors to cause the computer system to record a replay-able trace of execution of a multi-threaded process, the computer-executable instructions including instructions that are executable to cause the computer system to perform at least the following: identify a trace recording model that defines one or more orderable event types that are orderable across a plurality of threads of the multi-threaded process, as well as one or more non-orderable event types that are non-orderable across the plurality of threads; execute the plurality of threads concurrently across one or more processing units of the one or more processors; and during execution of the plurality of threads, record a separate replay-able trace for each thread independently, including, for each thread: recording initial state for the thread; recording at least one memory read performed by at least one processor instruction executed by the thread that takes memory as input; based on the thread executing an event having an orderable event type, recording a first monotonically increasing value into the replay-able trace, the monotonically increasing value ordering the event among another orderable event identifiable by a second monotonically increasing value recorded in another replay-able trace for another of the plurality of threads; and recording full key frames and lightweight key frames, and wherein a frequency of recording the full key frames or the lightweight key frames is adjustable.
 2. The computer system of claim 1, wherein recording initial state for the thread comprises recording an initial state of one or more processor registers prior to executing the thread.
 3. The computer system of claim 1, wherein recording a separate replay-able trace for each thread independently, includes, for at least one thread, recording one or more side effects of at least one non-deterministic processor instruction executed by the thread, including recording changes made by the non-deterministic processor instruction to one or more processor registers.
 4. The computer system of claim 1, wherein recording at least one memory read performed by at least one processor instruction comprises recording the at least one memory read based on use of a prediction algorithm.
 5. The computer system of claim 1, wherein recording at least one memory read performed by at least one processor instruction comprises using a shadow copy of memory that comprises only a subset of memory addressable by the process to predict a read value.
 6. The computer system of claim 1, wherein recording at least one memory read performed by at least one processor instruction comprises recording an identity of a memory page associated with the memory read.
 7. The computer system of claim 1, wherein recording initial state for the thread comprises recording a full key frame into the replay-able trace.
 8. The computer system of claim 1, wherein recording a separate replay-able trace for each thread independently, includes, for at least one thread, determining that a memory read need not be recorded based on use of a prediction algorithm.
 9. The computer system of claim 1, wherein recording a separate replay-able trace for each thread independently, includes, for each thread, recording into one or more reusable ring buffers.
 10. The computer system of claim 1, wherein recording a separate replay-able trace for each thread independently, includes, for each thread, recording one or more interruptions to execution of the thread.
 11. The computer system of claim 1, wherein the trace recording model defines the one or more orderable event types to include at least one of the following: a kernel call; full fences; acquires and releases; or memory loads.
 12. A method, implemented at a computer system that includes one or more processors, for recording a replay-able trace of execution of a multi-threaded process, the method comprising: identifying a trace recording model that defines one or more orderable event types that are orderable across a plurality of threads of the multi-threaded process, as well as one or more non-orderable event types that are non-orderable across the plurality of threads; executing the plurality of threads concurrently across one or more processing units of the one or more processors; and during execution of the plurality of threads, recording a separate replay-able trace for each thread independently, including, for each thread: recording initial state for the thread; recording at least one memory read performed by at least one processor instruction executed by the thread that takes memory as input; based on the thread executing an event having an orderable event type, recording a first monotonically increasing value into the replay-able trace, the monotonically increasing value ordering the event among another orderable event identifiable by a second monotonically increasing value recorded in another replay-able trace for another of the plurality of threads; and recording full key frames and lightweight key frames, and wherein a frequency of recording the full key frames or the lightweight key frames is adjustable.
 13. The method of claim 12, wherein recording initial state for the thread comprises recording an initial state of one or more processor registers prior to executing the thread.
 14. The method of claim 12, wherein recording a separate replay-able trace for each thread independently, includes, for at least one thread, recording one or more side effects of at least one non-deterministic processor instruction executed by the thread, including recording changes made by the non-deterministic processor instruction to one or more processor registers.
 15. The method of claim 12, wherein recording at least one memory read performed by at least one processor instruction comprises recording the at least one memory read based on use of a prediction algorithm.
 16. The method of claim 12, wherein recording at least one memory read performed by at least one processor instruction comprises using a shadow copy of memory to predict a read value.
 17. The method of claim 12, wherein recording initial state for the thread comprises recording a full key frame into the replay-able trace.
 18. The method of claim 12, wherein recording a separate replay-able trace for each thread independently, includes, for at least one thread, determining that a memory read need not be recorded based on use of a prediction algorithm.
 19. The method of claim 12, wherein recording a separate replay-able trace for each thread independently, includes, for each thread, recording into one or more reusable ring buffers.
 20. One or more hardware storage devices having stored thereon computer-executable instructions, the computer-executable instructions being executable by one or more processors of a computer system to cause the computer system to record a replay-able trace of execution of a multi-threaded process by causing the computer system to: identify a trace recording model that defines one or more orderable event types that are orderable across a plurality of threads of the multi-threaded process, as well as one or more non-orderable event types that are non-orderable across the plurality of threads; execute the plurality of threads concurrently across one or more processing units of the one or more processors; and during execution of the plurality of threads, record a separate replay-able trace for each thread independently, including, for each thread: recording initial state for the thread; recording at least one memory read performed by at least one processor instruction executed by the thread that takes memory as input; based on the thread executing an event having an orderable event type, recording a first monotonically increasing value into the replay-able trace, the monotonically increasing value ordering the event among another orderable event identifiable by a second monotonically increasing value recorded in another replay-able trace for another of the plurality of threads; and recording full key frames and lightweight key frames, and wherein a frequency of recording the full key frames or the lightweight key frames is adjustable. 